Mobile communication system, sgw, terminal communication method and control method

ABSTRACT

A bearer management device that performs control to reliably receive an incoming packet call that is made while a mobile terminal device is moving is provided. A bearer management device ( 10 ) includes an incoming call control unit ( 11 ) that, in the case where a mobility management device ( 30 ) manages a location of a mobile terminal device ( 40 ) as a result of movement of the mobile terminal device ( 40 ) whose location has been managed by a mobility management device ( 20 ), suspends processing of an incoming call to the mobile terminal device ( 40 ) made during movement of the mobile terminal device ( 40 ) until receiving a notification about completion of movement of the mobile terminal device ( 40 ) from the mobility management device ( 30 ), and resumes incoming call processing to the mobile terminal device ( 40 ) after receiving a notification about completion of movement of the mobile terminal device ( 40 ) from the mobility management device ( 30 ).

TECHNICAL FIELD

The present invention relates to a bearer management device and, forexample, relates to a bearer management device that performs incomingcall control for a mobile terminal device.

BACKGROUND ART

In the 3GPP (Third Generation Partnership Project) that defines astandard for mobile network systems, EPC (Evolved Packet Core) isspecified as the next generation mobile network system. The EPC is anetwork system that accommodates an LTE (Long Term Evolution) accessnetwork in addition to wireless access networks called the secondgeneration and the third generation.

Incoming packet call processing in the EPC is described hereinafter. In3rd Generation Partnership Project; Technical Specification GroupServices and System Aspects; General Packet Radio Service (GPRS)enhancements for Evolved Universal Terrestrial Radio Access Network(E-UTRAN) access (Release 12), 3GPP TS 23.401 V12.0.0 (2013-03), clauses5.3.4.3, 5.3.3.2), incoming packet call processing in the case where aUE (User Equipment) representing a user terminal is in the idle mode isdisclosed. The state where the UE is in the idle mode is the state wherethe UE is not connected with the EPC. In other words, a wireless bearerbetween the UE and the EPC is disconnected in this state. In such acase, when an incoming packet call is made to the UE, S-GW (ServingGateway), which is a bearer management device, sends an incoming callnotification message to MME (Mobility Management Entity) or SGSN(Serving GPRS Support Node) that manages the UE. Receiving the incomingcall notification message, the MME or SGSN sends a Paging message to eNB(evolved Node B) or NodeB, which is a base station, in order to call theUE. Receiving the Paging message, the eNB or NodeB sends a Pagingmessage to a plurality of UE located in the area managed by itself. TheUE to be called sends a response message to the eNB or NodeB andconnects to the EPC.

In this manner, even when an incoming packet call is made to the UE inthe idle mode which is not connected with the EPC, it is possible toperform data communication with the UE by calling the UE from thenetwork side.

CITATION LIST Patent Literature [NPL 1]

3rd Generation Partnership Project; Technical Specification GroupServices and System Aspects; General Packet Radio Service (GPRS)enhancements for Evolved Universal Terrestrial Radio Access Network(E-UTRAN) access (Release 12), 3GPP TS 23.401 V12.0.0 (2013-03), clauses5.3.4.3, 5.3.3.2

SUMMARY OF INVENTION Technical Problem

However, in the incoming packet call processing disclosed in the aboveliterature, the following problem occurs. Normally, when the UE movesout of a location registration area managed by the MME, the UE sends alocation registration request (Tracking Area Update Request) message toa new MME that manages a location registration area to which the UE isto move. Receiving the location registration request message, the newMME performs location registration of the UE. After the locationregistration in the new MME is done, the UE becomes the state where itis registered in the new MME that manages the location registration areato which it is to move.

When an incoming packet call arrives to the UE after the UE sends thelocation registration request message and before processing for movementis done in the new MME, the S-GW sends the incoming call notificationmessage to the old MME that has managed the location of the UE beforemovement. Receiving the incoming call notification message, the old MMEsends a Paging message to a base station under its control; however,because the UE to be called has moved out to the area managed by the newMME, it is not possible to call the UE. In other words, when an incomingpacket call is made while the UE is during its movement which involves achange in the MME, the problem that the UE cannot receive the incomingpacket occurs.

An exemplary object of the present invention is to provide a bearermanagement device, a mobility management device, a mobile terminaldevice, a communication system, an incoming call processing method, amobility management method and program that perform control so as toreliably receive an incoming packet call that is made during movement ofthe mobile terminal device.

Solution to Problem

A bearer management device according to a first exemplary aspect of theinvention includes an incoming call control unit that, in a case where asecond mobility management device manages a location of a mobileterminal device as a result of movement of the mobile terminal devicewhose location has been managed by a first mobility management device,suspends processing of an incoming call to the mobile terminal devicemade during movement of the mobile terminal device until receiving anotification about completion of movement of the mobile terminal devicefrom the second mobility management device, and resumes incoming callprocessing to the mobile terminal device after receiving a notificationabout completion of movement of the mobile terminal device from thesecond mobility management device.

A mobility management device according to a second exemplary aspect ofthe invention is a mobility management device that manages movement of amobile terminal device, including a communication unit that, whenreceiving an incoming call notification message to the mobile terminaldevice sent from a bearer management device in a case where the mobileterminal device whose location has been managed by the mobilitymanagement device has moved and a location of the mobile terminal deviceis managed by another mobility management device, sends a movementnotification message indicating that the mobile terminal device hasmoved to said another mobility management device to the bearermanagement device.

A mobile terminal device according to a third exemplary aspect of theinvention includes a communication unit that, when the mobile terminaldevice moves out of an area managed by a first mobility managementdevice from a state where its location has been managed by the firstmobility management device, sends a location registration requestmessage to a second mobility management device and, when an incomingcall is made before location registration of the mobile terminal deviceis completed in the second mobility management device, receives dataaddressed to the mobile terminal device using a wireless resource usedwhen sending the location registration request message.

A communication system according to a fourth exemplary aspect of theinvention includes a first mobility management device that manages alocation of a mobile terminal device located in a first area, a secondmobility management device that manages a location of a mobile terminaldevice located in a second area different from the first area, and abearer management device that sends an incoming call notificationmessage to the first or second mobility management device when anincoming call to the mobile terminal device is made, wherein, in a casewhere the second mobility management device manages a location of themobile terminal device as a result of movement of the mobile terminaldevice having been located in the first area to the second area, thebearer management device suspends processing of an incoming call to themobile terminal device made during movement of the mobile terminaldevice until receiving a notification about completion of movement ofthe mobile terminal device from the second mobility management device,and resumes incoming call processing to the mobile terminal device afterreceiving a notification about completion of movement of the mobileterminal device from the second mobility management device.

An incoming call processing method according to a fifth exemplary aspectof the invention includes, in a case where a second mobility managementdevice manages a location of a mobile terminal device as a result ofmovement of the mobile terminal device whose location has been managedby a first mobility management device, suspending processing of anincoming call to the mobile terminal device made during movement of themobile terminal device until receiving a notification about completionof movement of the mobile terminal device from the second mobilitymanagement device, and resuming incoming call processing to the mobileterminal device after receiving a notification about completion ofmovement of the mobile terminal device from the second mobilitymanagement device.

A mobility management method according to a sixth exemplary aspect ofthe invention is a mobility management method in a mobility managementdevice that manages movement of a mobile terminal device, including,when receiving an incoming call notification message to the mobileterminal device from a bearer management device in a case where themobile terminal device whose location has been managed by the mobilitymanagement device has moved and a location of the mobile terminal deviceis managed by another mobility management device, sending a movementnotification message indicating that the mobile terminal device hasmoved to said another mobility management device to the bearermanagement device.

A program according to a seventh exemplary aspect of the inventioncauses a computer to execute, in a case where a second mobilitymanagement device manages a location of a mobile terminal device as aresult of movement of the mobile terminal device whose location has beenmanaged by a first mobility management device, a step of suspendingprocessing of an incoming call to the mobile terminal device made duringmovement of the mobile terminal device until receiving a notificationabout completion of movement of the mobile terminal device from thesecond mobility management device, and a step of resuming incoming callprocessing to the mobile terminal device after receiving a notificationabout completion of movement of the mobile terminal device from thesecond mobility management device.

Advantageous Effects of Invention

According to the exemplary aspects of the present invention, it ispossible to provide a bearer management device, a mobility managementdevice, a mobile terminal device, a communication system, an incomingcall processing method, a mobility management method and program thatperform control to reliably receive an incoming packet call that is madeduring movement of the mobile terminal device.

The above and other objects, features and advantages of the presentinvention will become more fully understood from the detaileddescription given hereinbelow and the accompanying drawings which aregiven by way of illustration only, and thus are not to be considered aslimiting the present invention.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a configuration diagram of a communication system according toa first exemplary embodiment;

FIG. 2 is a configuration diagram of a mobile communication systemspecified in the 3GPP according to a second exemplary embodiment;

FIG. 3 is a configuration diagram of a mobile communication systemspecified in the 3GPP according to the second exemplary embodiment;

FIG. 4 is a configuration diagram of a mobile communication systemspecified in the 3GPP according to the second exemplary embodiment;

FIG. 5 is configuration diagram of SGW according to the second exemplaryembodiment;

FIG. 6 is a diagram showing a flow of connection processing whenconnecting UE to a mobile communication system according to the secondexemplary embodiment;

FIG. 7 is a diagram showing a flow of processing when an incoming packetcall is made to UE according to the second exemplary embodiment;

FIG. 8 is a diagram showing a flow of processing when an incoming packetcall is made to UE according to a third exemplary embodiment;

FIG. 9 is a diagram showing a flow of processing when an incoming packetcall is made to UE according to a fourth exemplary embodiment; and

FIG. 10 is a diagram showing a flow of processing when an incomingpacket call is made to UE according to a fifth exemplary embodiment.

DESCRIPTION OF EMBODIMENTS First Exemplary Embodiment

An exemplary embodiment of the present invention is describedhereinafter with reference to the drawings. A configuration example of acommunication system according to a first exemplary embodiment isdescribed hereinafter with reference to FIG. 1. The communication systemin FIG. 1 includes a bearer management device 10, a mobility managementdevice 20, a mobility management device 30, and a mobile terminal device40. The mobility management device 20 manages the location of the mobileterminal device located in a location registration area 21. The mobilitymanagement device 30 manages the location of the mobile terminal devicelocated in a location registration area 31. Further, in FIG. 1, themobile terminal device 40 is moving from the location registration area21 to the location registration area 31. Note that, in FIG. 1, awireless base station that wirelessly communicates with the mobileterminal device 40 is not shown. As the mobile terminal device 40 movesfrom the location registration area 21 to the location registration area31, the mobility management device that manages the mobile terminaldevice 40 changes from the mobility management device 20 to the mobilitymanagement device 30. When registration of the mobile terminal device 40is completed, the mobility management device 30 notifies the bearermanagement device 10 about the completion of movement of the mobileterminal device 40.

A configuration example of the bearer management device 10 is describedhereinafter. The bearer management device 10 includes an incoming callcontrol unit 11. The case where an incoming packet call is made to themobile terminal device 40 when the mobile terminal device 40 has movedfrom the location registration area 21 to the location registration area31 and before registration of the mobile terminal device 40 is completedin the mobility management device 30 is described hereinafter. In thiscase, even when an incoming call is made to the mobile terminal device40, the incoming call control unit 11 suspends incoming call processingfor the mobile terminal device 40 until it receives a notification aboutthe completion of movement of the mobile terminal device 40 from themobility management device 30. After receiving a notification about thecompletion of movement of the mobile terminal device 40 from themobility management device 30, the incoming call control unit 11 resumesincoming call processing for the mobile terminal device 40. For example,the incoming call control unit 11 may acquire information that themobile terminal device 40 is during its movement from the mobilitymanagement device 20 when performing incoming call processing for themobility management device 20.

The incoming call processing is processing that notifies an incomingcall message to the mobility management device that manages the mobileterminal device 40, and sends data addressed to the mobile terminaldevice 40 to the mobile terminal device 40, for example. Suspending theincoming call processing may means that, when the incoming call controlunit 11 detects that the mobile terminal device 40 is moving, itsuspends transition to processing of sending data (user data) addressedto the mobile terminal device 40 to the mobile terminal device 40 and,after receiving a notification about the completion of movement of themobile terminal device 40, sends the data addressed to the mobileterminal device 40 to the mobile terminal device 40. Alternatively, itmay mean that the incoming call control unit 11 suspends transmission ofan incoming call message to the mobility management device until itreceives a notification about the completion of movement of the mobileterminal device 40 from the mobility management device 30. Duringmovement of the mobile terminal device 40 may be a period from when themobile terminal device 40 sends a location registration request messageto the mobility management device 30 that manages the locationregistration area 31 to which it is to move to when the mobilitymanagement device 30 notifies a message indicating the completion ofmovement of the mobile terminal device 40 to the bearer managementdevice 10.

Suspending the incoming call processing may be temporarily suspendingthe incoming call processing, temporarily stopping the incoming callprocessing, ceasing the incoming call processing with the assumption ofresuming the incoming call processing, deferring the execution of theincoming call processing and the like.

As described above, with use of the communication system in FIG. 1, evenwhen an incoming packet call is made to the mobile terminal device 40while the mobile terminal device 40 is during its movement whichinvolves a change in the mobility management device that manages itslocation, the mobile terminal device 40 can receive the packetcommunication. In other words, the bearer management device 10 canresume the incoming call processing for the mobile terminal device 40after receiving a notification about the completion of movement from themobility management device 30 that manages the location registrationarea to which the mobile terminal device 40 moves. Therefore, even whenan incoming packet call is made before processing for movement of themobile terminal device 40 is not done, the bearer management device 10can notify the mobile terminal device 40 about an incoming packet call.

Second Exemplary Embodiment

A configuration example of a communication system according to a secondexemplary embodiment of the invention is described hereinafter withreference to FIG. 2. In FIG. 2, a mobile communication system specifiedin the 3GPP is described as a communication system. The communicationsystem in FIG. 2 includes PGW (Packet Data Network GateWay) 75, SGW(Serving GateWay) 15, MME 25, MME 35, UE 45, eNB 55 and eNB 65.

The UE 45 is a communication device that is specified as a mobileterminal device in the 3GPP. The UE 45 may be a cellular phone, asmartphone, a tablet terminal, a personal computer with a communicationfunction or the like, for example. Further, the UE 45 may be an M2M(Machine To Machine) device that performs communications in anautonomous manner. The M2M device may be a device that does not oftenmove such as an automatic vending machine or an electrical appliancehaving a communication function, or a watch worn by a user and the like,for example.

The eNB 55 and eNB 65 are node devices specified as base stations in the3GPP. Each of the eNB 55 and eNB 65 forms a wireless communication areaand communicates with the UE that is located in the wirelesscommunication area managed by itself.

The PGW 75 is a node device that is located at the boundary between themobile communication system and the external network. The PGW 75 sendsdata sent from the external network to the node device in the mobilecommunication system. The PGW 75 establishes a communication bearer withthe SGW 15. The communication bearer may be referred to as acommunication channel, a communication path or the like, for example.The PGW 75 sends data sent from the external network to the SGW 15through the communication bearer.

The bearer management device 10 in FIG. 1 is specified as the SGW 15 inthe 3GPP. When the SGW 15 receives a notification about an incomingpacket call to the UE 45, it notifies an incoming call message to theMME 25 or MME 35. Further, the SGW 15 sends data addressed to the UE 45to the eNB 55 or eNB 65 that communicates with the mobile terminaldevice 45.

The mobility management devices 20 and 30 in FIG. 1 are specified as theMME 25 and MME 35 in the 3GPP. Each of the MME 25 and MME 35 defines alocation registration area that manages the location of the UE. In thelocation registration area managed by each of the MME 25 and MME 35, aplurality of eNB may be located. In other words, the locationregistration area may include a plurality of wireless communicationareas formed by eNB.

When the UE 45 moves from the location registration area defined by theMME 25 to the location registration area defined by the MME 35, the UE45 sends a location registration request message to the MME 35.Receiving the location registration request message sent from the UE 45,the MME 35 performs processing for movement of the UE 45. The processingfor movement of the UE 45 is processing that the MME 35 registers the UE45 as a device to be managed, for example. Further, when the MME 35receives the location registration request message sent from the UE 45,it sends a message notifying that the UE 45 has moved to the locationregistration area defined by the MME 35 to the MME 25 that manages thelocation registration area from which the UE 45 moves. The UE 45 may addan identifier of the MME 25 that manages the location registration areabefore movement to the location registration request message for the MME35. The MME 35 can thereby detect the MME 25 that manages the locationregistration area from which the UE 45 moves. The MME 25 receives thenotification message from the MME 35 and can thereby detect that the UE45 has moved to the location registration area defined by the MME 35.

After the processing for movement of the UE 45 is completed, the MME 35sends a message indicating the completion of movement processing of theUE 45 to the SGW 15. In the case where an incoming packet call is madeto the UE 45, the SGW 15 sends an incoming call notification message tothe MME 25 until a message indicating the completion of movementprocessing of the UE 45 is sent from the MME 35.

There is a case where the MME 25 receives an incoming call notificationmessage to the UE 45 from the SGW 15 after it receives a messageindicating the movement of the UE 45 from the MME 35. In such a case,the MME 25 sends a message notifying that the UE 45 has moved out to theSGW 15.

By receiving the message notifying that the UE 45 has moved out from theMME 25, the SGW 15 detects that the UE 45 is during its movement whichinvolves a change in the MME. When the SGW 15 detects that the UE 45 isduring its movement which involves a change in the MME, the SGW 15temporarily stores data addressed to the UE 45 into a buffer. When theSGW 15 receives a message notifying the completion of movement of the UE45 from the MME 35, the SGW 15 sends an incoming call notificationmessage to the UE 45 to the MME 35. After that, the SGW 15 sends thedata addressed to the UE 45 to the UE 45.

Although the mobility management devices 20 and 30 are described asbeing the MME 25 and 35 above, the mobility management devices 20 and 30may be SGSN 27 and 37 as shown in FIG. 3, The SGSN 27 and 37 are nodedevices that manage the location of the UE that communicates with awireless access network called 2G or 3G. The SGSN 27 and 37 connect to2G/3G wireless control devices 57 and 67 in the wireless access networkcalled 2G or 3G in the 3GPP. The 2G/3G wireless control device in thewireless access network called 2G or 3G may be called RNC (Radio NetworkController), for example. The configuration shown in FIG. 3 is the sameas that of FIG. 2 except that the MME 25 and 35 are replaced with theSGSN 27 and 37, and the eNB 55 and 65 are replaced with the 2G/3Gwireless control devices 57 and 67.

Further, the SGW 15 may connect to the MME 25 and the SGSN 37 as shownin FIG. 4. In other words, the SGW 15 may be located in the system wherethe MME and the SGSN coexist. The configuration shown in FIG. 4 is thesame as that of FIG. 2 except that the MME 35 in FIG. 2 is replaced withthe SGSN 37, and the eNB 65 is replaced with the 2G/3G wireless controldevice 67.

A configuration example of the SGW 15 according to the second exemplaryembodiment of the invention is described hereinafter with reference toFIG. 5. The SGW 15 includes an incoming call control unit 16 and a dataaccumulation unit 17. The incoming call control unit 16 is the same asthe incoming call control unit 11 in FIG. 1.

When a message notifying the movement of the UE 45 is sent from the MME25 that manages the location registration area from which the UE 45moves, the incoming call control unit 16 temporarily stores dataaddressed to the UE 45 into the data accumulation unit 17. Further, whena message notifying the completion of movement of the UE 45 is sent fromthe MME 35 that manages the location registration area to which the UE45 moves, the incoming call control unit 16 sends an incoming callmessage to the UE 45 to the MME 35. Further, when a wireless bearer isestablished between the UE 45 and the eNB 65, the incoming call controlunit 16 sends the data stored in the data accumulation unit 17 to the UE45 through the eNB 65.

Hereinafter, a flow of processing to connect the UE to the mobilecommunication system according to the second exemplary embodiment of theinvention is described with reference to FIG. 6. First, when a powerswitch is pressed by a user and a power is turned on, the UE 45 sends anAttach Request message as the location registration request message tothe eNB 55 (S11). Next, the eNB 55 sends the Attach Request message sentfrom the UE 45 to the MME 25 (S12). Receiving the Attach Requestmessage, the MME 25 generates location registration information of theUE 45. The location registration information contains informationindicating that the UE 45 is located within the location registrationarea managed by its own device or subscriber information of the UE 45,for example. The subscriber information of the UE 45 may be acquiredfrom a subscriber information management device (not shown) that isplaced in the mobile communication system. The subscriber informationmanagement device is specified as HSS (Home Subscriber Server) in the3GPP, for example. Then, the MME 25 notifies the subscriber informationof the UE 45 to the SGW 15 using a Create Session Request message (S13).Then, the SGW 15 sends a Create Session Response message to the MME 25as a response message to the Create Session Request message (S14). Byreceiving the Create Session Request message, the SGW 15 can identifythe MME that manages the location of the UE 45. Further, by thetransmission of the Create Session Response message, a session for theUE 45 is established between the MME 25 and the SGW 15.

Receiving the Create Session Response message, the MME 25 sends anAttach Accept message to the eNB 55 as a response signal to the AttachRequest message (S15). By the transmission of the Attach Accept message,the MME 25 completes registration processing of the UE 45. Thecompletion of registration processing of the UE 45 means the completionof movement processing of the UE 45. After that, the eNB 55 sends anAttach Accept message to the UE 45 (S16).

By receiving the Attach Accept message, the UE 45 becomes connected tothe mobile communication system. The state where the UE 45 is connectedto the mobile communication system may be referred to as the state wherethe UE 45 is attached to the mobile communication system.

Although the flow of processing when the power of the UE 45 is turned onis described above, the same processing is executed also when thelocation registration area where the UE 45 is located changes in orderto generate location registration information in a new MME. When thelocation registration area where the UE 45 is located changes, the UE 45sends a Tracking Area Update Request message instead of the AttachRequest message. Further, the MME 25 and the SGW 15 send and receiveModify Bearer Request/Modify Bearer Response messages instead of theCreate Session Request/Create Session Response messages.

Hereinafter, a flow of processing performed when an incoming packet callis made to the UE 45 while the UE 45 is during its movement whichinvolves a change in the MME according to the second exemplaryembodiment of the invention is described with reference to FIG. 7. Inthis example, it is assumed that the processing of FIG. 6 is completed,and the UE 45 is located in the location registration area managed bythe MME 25.

First, when the UE 45 detects that it has moved from the locationregistration area managed by the MME 25 to another location registrationarea, the UE 45 sends a Tracking Area Update Request message to the eNB65 that manages the location registration area to which it has moved(S21). The UE 45 may detect that the location registration area haschanged by receiving annunciation information delivered from the eNB 65.Specifically, the UE 45 may detect that the location registration areahas changed when the location registration area delivered from the eNB55 before movement and the location registration area delivered from theeNB 65 after movement are different from each other.

Next, the eNB 65 sends a Tracking Area Update Request message for the UE45 to the MME 35 that manages the location registration area includingthe communication area of its own device (S23). At the same time, S1Connection is established between the eNB 65 and the MME 35 forcommunication of a control message between the UE 45 and the MME 35. Itis assumed that the Tracking Area Update Request message contains theidentifier of the MME 25 that used to manage the location registrationarea from which the UE 45 has moved.

Then, the MME 35 sends a Context Request message requesting the transferof the location registration information to the MME 25 in order toacquire the location registration information of the UE 45 from the MME25 (S24). By the transmission of the Context Request message requestingthe transfer of the location registration information from the MME 35,the MME 25 can detect that the UE 45 has moved out of the locationregistration area managed by itself. Further, by receiving the ContextRequest message sent from the from the MME 35, the MME 25 can detectthat the UE 45 has moved to the location registration area managed bythe MME 35.

It is assumed that an incoming packet call to the UE 45 is notified tothe SGW 15 after the Context Request message is sent from the MME 35 tothe MME 25 in Step S24 (S25). Incoming packet call is notified from theexternal network to the SGW 15 via the PGW 75.

The SGW 15 has been notified in the connection processing in FIG. 6 thatthe UE 45 is located in the location registration area managed by theMME 25. Therefore, to notify an incoming packet call to the UE 45, theSGW 15 sends a Downlink Data Notification message to the MME 25 in orderto notify an incoming packet call to the UE 45 (S26).

The MME 25 has detected that the UE 45 is during its movement byreceiving the Context Request message in Step S24. Therefore, the MME 25cannot temporarily perform call attempt to the UE 45, that is,temporarily rejects the Downlink Data Notification message. Then, theMME 25 sets Cause indicating that the UE 45 is during its movement andcall attempt to the UE 45 is temporarily impossible and sends a DownlinkData Notification Acknowledge message in response to the Downlink DataNotification message (S27). To the Downlink Data NotificationAcknowledge message, “Cause=Temporarily Rejected due to mobility” is setas Cause setting. “Cause=Temporarily Rejected due to mobility” indicatesthat information indicating that the UE is moving and call attempt istemporarily unavailable (temporarily rejected) is set to Cause.

Receiving the Downlink Data Notification Acknowledge message to which“Cause=Temporarily Rejected due to mobility” is set, the SGW 15 suspendsincoming packet call processing, and starts a timer (locally configuredguard timer) for retransmitting the Downlink Data Notification message,continuing buffering of the packet addressed to the UE 45.

Then, the MME 25 executes the operation as the MME that manages thelocation registration area from which the UE 45 moves in the TrackingArea Update Request message. Specifically, the MME 25 sends a ContextResponse message to the MME 35 as a response message to the ContextRequest message in Step S24 (S28). The MME that manages the locationregistration area from which the UE 45 moves may be referred to as OldMME. On the other hand, the MME that manages the location registrationarea to which the UE 45 moves may be referred to as New MME. The MME 25notifies the location registration information of the UE 45 to the MME35 using the Context Response message. The MME 35 sends a ContextAcknowledge message to the MME 25 as a response message to the ContextResponse message (S29).

Then, the MME 35 sends a Modify Bearer Request message to the SGW 15 inorder to notify switching of the session established between the MME 25and the SGW 15 (S30). The session established between the MME 25 and theSGW 15 is the session that has been established in Steps S13 and S14 ofFIG. 6. The SGW 15 detects that the movement processing of the UE 45 iscompleted in the MME 35 by receiving the Modify Bearer Request message.The MME 35 may send an identifier that identifies the sessionestablished between the MME 25 and the SGW 15 to the SGW 15 and therebynotify switching of the session established between the MME 25 and theSGW 15. The identifier that identifies the session established betweenthe MME 25 and the SGW 15 may be contained in the Context Responsemessage in Step S28.

The SGW 15 sends a Modify Bearer Response message to the MME 35 as aresponse message to the Modify Bearer Request message (S31). At the sametime, the SGW 15 stops the timer (locally configured guard timer) thathas been started when receiving the Downlink Data NotificationAcknowledge message in Step S27.

Receiving the Modify Bearer Response message, the MME 35 sends aTracking Area Update Accept message to the eNB 65 as a response messageto Step S23 (S32). Then, the eNB 65 sends the sent Tracking Area UpdateAccept message to the UE 45 (S33).

After that, the MME 35 releases the S1 Connection that has beenestablished between the MME 35 and the eNB 65 (S34).

Then, the SGW 15 sends a Downlink Data Notification message to the MME35 that manages the location registration area to which the UE 45 movesin order to notify an incoming packet call to the UE 45 (S35). Thus, inStep S35, the processing of sending the Downlink Data Notificationmessage to the MME 25 in Step S26 is performed for the MME 35 thatmanages the location registration area to which the UE 45 moves. Then,the MME 35 sends a Paging message to the eNB 65 in order to perform callattempt to the UE 45 (S36), and the eNB 65 sends a Paging message to theUE located in the communication area under its control (S37). In thismanner, after moving to the new location registration area, the UE 45can receive a notification about the incoming packet call that has beenmade during its movement.

In the case where the timer (locally configured guard timer) that hasbeen started when the Downlink Data Notification Acknowledge message isreceived in Step S27 expires before receiving the Modify Bearer Requestmessage, the SGW 15 may end the incoming packet call processing to theUE 45. Alternatively, the SGW 15 may send the Downlink Data Notificationmessage to the MME 25 again to continue the incoming packet callprocessing.

In the case where the timer (locally configured guard timer) that hasbeen started when the Downlink Data Notification Acknowledge message isreceived in Step S27 expires without receiving the Modify Bearer Requestmessage, the SGW 15 may release the buffered packet addressed to the UE45.

As described above, with use of the communication system according tothe second exemplary embodiment of the invention, even when an incomingpacket call is made to the UE 45 while the UE 45 is during its movementwhich involves a change in the MME and the movement processing of the UE45 has not completed in the new MME, the UE 45 can normally receive anincoming packet call notification.

Further, in the case where the MME 35 is replaced with the SGSN 37 andthe eNB 65 is replaced with the 2G/3G wireless control device 67 asshown in FIGS. 3 and 4, the Tracking Area Update Request message inSteps S21 and S23 is replaced with the Routing Area Update Requestmessage. Further, the Tracking Area Update Accept message in Steps S32and S33 is replaced with the Routing Area Update Accept message. If theMME 25 and the SGSN 37 activate ISR (Idle-mode signaling reduction), thecontinuation of the incoming packet call processing performed in StepS35 may be carried out by both of the MME 25 and the SGSN 37.

Third Exemplary Embodiment

Hereinafter, a flow of processing performed when an incoming packet callis made to the UE 45 while the UE 45 is during its movement whichinvolves a change in the MME according to the third exemplary embodimentof the invention is described with reference to FIG. 8. Steps S41 to S49are the same as Steps S21 to S29 in FIG. 7 and thus not redundantlydescribed in detail. Further, when executing the processing of FIG. 8,it is assumed that the processing of FIG. 6 is completed, and the UE 45is located in the location registration area managed by the MME 25.

After sending the Context Acknowledge message to the MME 25 in Step S49,the MME 35 sends a Modify Bearer Request message to the SGW 15 (S50).The SGW 15 sets information of “SGW requested active flag=ON” to theModify Bearer Response message and sends it to the MME 35 (S51).

Receiving the information of “SGW requested active flag=ON”, the MME 35maintains the S1 Connection between the eNB 65 and the MME 35 that hasbeen established for Attach processing or Tracking Area Updateprocessing without releasing it. Further, the MME 35 also maintains theRRC (Radio Resource Control) connection between the UE 45 and the eNB 65that has been established for Attach processing or Tracking Area Updateprocessing. When the SGW 15 receives a Modify Bearer Request indicatingthe completion of movement of the UE after detecting that the UE towhich an incoming packet call notified in Step S45 is made is during itsmovement, it sets information of “SGW requested active flag=ON” to theModify Bearer Response message and sends it to the MME 35.

Receiving the Modify Bearer Response message, the MME 35 sends aTracking Area Update Accept message to the eNB 65 as a response messageto Step S43 (S52). The eNB 65 then sends the sent Tracking Area UpdateAccept message to the UE 45 (S53). Because the MME 35 has received theinformation of “SGW requested active flag=ON”, it does not execute S1Connection release processing. Further, at the same time as sending theTracking Area Update Accept message, the MME 35 sends a wireless packetbearer establishment request message to the eNB 65 through themaintained S1 Connection. The wireless packet bearer is a bearer that isused for communication of user data such as audio data, image data orvideo data between the UE 45 and the eNB 65.

Receiving the wireless packet bearer establishment request message, theeNB 65 establishes a wireless packet bearer between the UE 45 and theeNB 65 using the RRC connection (S55). After establishing the wirelesspacket bearer, the eNB 65 sends a wireless packet bearer establishmentresponse message to the MME 35 (S56). The wireless packet bearerestablishment response message contains TEID (eNB Tunnel End PointIdentifier) of the eNB 65.

Receiving the wireless packet bearer establishment response message, theMME 35 sends a Modify Bearer Request message to which the TEID of theeNB 65 is set to the SGW 15 (S57).

Then, the SGW 15 sends a Modify Bearer Response message to the MME 35 asresponse message to the Modify Bearer Request message (S58). The SGW 15then sends the data addressed to the UE 45 to the TEID of the eNB 65 setto the Modify Bearer Request message. The eNB 65 sends the dataaddressed to the UE 45 sent from the SGW 15 to the UE 45 through thewireless packet bearer (S59).

As described above, in the flow of processing in FIG. 8, after the MME35 sends the Tracking Area Update Accept message, it does not release S1Connection and sends the wireless packet bearer establishment requestmessage to the eNB 65 using the maintained S1 Connection. The UE 45thereby remains connected with the mobile communication system, and theMME 35 can skip the processing of sending the Paging message and callattempt to the UE 45, which is described in FIG. 7.

In FIG. 7, the MME 35 releases S1 Connection with the eNB 65. The UE 45thereby becomes disconnected from the mobile communication system, thatis, becomes separated from the mobile communication system. Therefore,the MME 35 needs to send the Paging message to call the UE 45.

On the other hand, in FIG. 8, the S1 Connection between the MME 35 andthe eNB 65 is maintained, and further the RRC Connection between the UE45 and the eNB 65 is maintained. Therefore, the MME 35 does not need toexecute the processing of call attempt to the UE 45, and it is possibleto skip the processing of sending the Paging message.

The MME 35 sends the Paging message to all the eNB located in thelocation registration area managed by itself. Further, the eNB that hasreceived the Paging message sends the Paging message to all the UElocated in the communication area under its control. Therefore, theprocessing of sending the Paging message is heavy-load processing in themobile communication system. Thus, by omitting the transmission of thePaging message in FIG. 8, it is possible to reduce the load in themobile communication system.

Fourth Exemplary Embodiment

Hereinafter, a flow of processing performed when an incoming packet callis made to the UE 45 while the UE 45 is during its movement whichinvolves a change in the MME according to the fourth exemplaryembodiment of the invention is described with reference to FIG. 9. StepsS61 to S67 are the same as Steps S21 to S27 in FIG. 7 and Steps S41 toS47 in FIG. 8 and thus not redundantly described in detail. Further,when executing the processing of FIG. 9, it is assumed that theprocessing of FIG. 6 is completed, and the UE 45 is located in thelocation registration area managed by the MME 25.

The MME 25 sends a Context Response message to the MME 35 as a responsemessage to the Context Request message sent from the MME 35 in Step S64(S68). The MME 25 sends the Context Response message to which “ActiveFlag=ON” is set to the MME 35 in order to notify that it is necessary toestablish a wireless packet bearer. Then, the MME 35 sends a ContextAcknowledge message to the MME 25 as a response message to the ContextResponse message (S69).

Steps S70 to S77 are the same as Steps S52 to S59 in FIG. 8 and thus notredundantly described in detail. In Steps S70 to S77, the processing ofestablishing a wireless packet bearer between the UE 45 and the eNB 65is performed without releasing the S1 Connection, just like theprocessing of FIG. 8.

As described above, in the processing of FIG. 9, a message that servesas a trigger to establish a wireless packet bearer is sent to the MME 35from the MME 25, not from the SGW 15. Therefore, in the processing ofFIG. 9, it is possible to skip the transmission and reception of theModify Bearer Request/Modify Bearer Response messages in Steps S50 andS51 in the processing of FIG. 8. Further, in the processing of FIG. 9,it is possible to skip the processing of sending the Paging message,just like the processing of FIG. 8.

Fifth Exemplary Embodiment

Hereinafter, a flow of processing performed when the UE 45 makes itsmovement which involves a change in the MME after an incoming packetcall is notified according to the fifth exemplary embodiment of theinvention is described with reference to FIG. 10. When executing theprocessing of FIG. 10, it is assumed that the processing of FIG. 6 iscompleted, and the UE 45 is located in the location registration areamanaged by the MME 25.

First, the SGW 15 receives an incoming packet call to the UE 45 (S81).The SGW 15 receives an incoming packet call that is sent from theexternal network through the PGW 75. The SGW 15 has been notified in theconnection processing in FIG. 6 that the UE 45 is located in thelocation registration area managed by the MME 25. Therefore, to notifyan incoming packet call to the UE 45, the SGW 15 sends a Downlink DataNotification message to the MME 25 (S82).

Next, the MME 25 sends a Downlink Data Notification Acknowledge messageas a response message to the Downlink Data Notification message (S83).The MME 25 then sends a Paging message to the eNB 55 for call attempt tothe UE 45 (S84), and the eNB 55 sends the Paging message to the UElocated in the communication area under its control (S85).

It is assumed that, immediately before the eNB 55 sends the Pagingmessage or immediately after the eNB 55 sends the Paging message in StepS85, the UE 45 moves out of the wireless communication area managed bythe eNB 55 and out of the location registration area managed by the MME25. In such a case, the UE 45 cannot receive the Paging message.

When the UE 45 moves out of the location registration area managed bythe MME 25 and into the location registration area managed by the MME35, the UE 45 sends a Tracking Area Update Request message to the eNB 65located in the location registration area managed by the MME 35 (S86).

Then, the eNB 65 sends a Tracking Area Update Request message for the UE45 to the MME 35 that manages the location registration area includingthe communication area of its own device (S88). At the same time, S1Connection is established between the eNB 65 and the MME 35 forcommunication of a control message. It is assumed that the Tracking AreaUpdate Request message contains the identifier of the MME 25 that usedto manage the location registration area from which the UE 45 has moved.

Then, the MME 35 sends a Context Request message requesting the transferof the location registration information to the MME 25 in order toacquire the location registration information of the UE 45 from the MME25 (S89). By the transmission of the Context Request message requestingthe transfer of the location registration information of the UE 45 fromthe MME 35, the MME 25 can detect that the UE 45 has moved out of thelocation registration area managed by itself. Further, by receiving theContext Request message sent from the from the MME 35, the MME 25 candetect that the UE 45 has moved to the location registration areamanaged by the MME 35.

The MME 25 has detected that the UE 45 is during its movement byreceiving the Context Request message in Step S89. Therefore, the MME 25stops call attempt to the UE 45 and temporarily rejects the DownlinkData Notification. Then, the MME 25 sets Cause indicating that the UE 45is during its movement and call attempt to the UE 45 is temporarilyimpossible (temporarily rejected) and sends a Downlink Data NotificationFailure Indication message indicating a failure in incoming packet callnotification (S90). To the Downlink Data Notification Acknowledgemessage, “Cause=Temporarily Rejected due to mobility” is set as Causesetting.

Receiving the Downlink Data Notification Failure Indication message towhich “Cause=Temporarily Rejected due to mobility” is set, the SGW 15suspends incoming packet call processing, and starts a timer (locallyconfigured guard timer) for retransmitting the Downlink DataNotification message, continuing buffering of the packet addressed tothe UE 45.

The MME 25 notifies the location registration information of the UE 45to the MME 35 using the Context Response message as a response messageto the Context Request message (S91). The MME 25 sends the ContextResponse message to which “Active Flag=ON” is set to the MME 35 in orderto notify that call attempt to the UE 45 has been performed. Then, theMME 35 sends a Context Acknowledge message to the MME 25 as a responsemessage to the Context Response message (S92).

Steps S93 to S100 are the same as Steps S70 to S77 in FIG. 9 and thusnot redundantly described in detail.

As described above, in the processing of FIG. 10, even in the case wherethe Paging message cannot be notified to the UE 45 because the UE 45 hasstarted its movement which involves a change in the MME, it is possibleto notify the movement of the UE 45 from the MME 35 that manages thelocation registration area to which the UE 45 moves to the MME 25 thatmanages the location registration area from which the UE 45 moves.Further, the MME 25 can notify the MME 35 that the processing ofnotifying the Paging message to the UE 45 has been executed. The MME 35can thereby detect that an incoming packet call is made to the UE 45.Thus, the MME 35 instructs establishment of a wireless bearer betweenthe UE 45 and the eNB 65, and thereby the SGW 15 can transmit dataaddressed to the UE 45 to the UE 45.

Although the present invention is described as a hardware configurationin the above exemplary embodiments, the present invention is not limitedthereto. The present invention may be implemented by causing a CPU(Central Processing Unit) to execute a computer program to perform theprocessing of the bearer management device and the mobility managementdevice.

The above-described program can be stored and provided to the computerusing any type of non-transitory computer readable medium. Thenon-transitory computer readable medium includes any type of tangiblestorage medium. Examples of the non-transitory computer readable mediuminclude magnetic storage media (such as floppy disks, magnetic tapes,hard disk drives, etc.), optical magnetic storage media (e.g.magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R/W, andsemiconductor memories (such as mask ROM, PROM (Programmable ROM), EPROM(Erasable PROM), flash ROM, RAM (Random Access Memory), etc.). Theprogram may be provided to a computer using any type of transitorycomputer readable medium. Examples of the transitory computer readablemedium include electric signals, optical signals, and electromagneticwaves. The transitory computer readable medium can provide the programto a computer via a wired communication line such as an electric wire oroptical fiber or a wireless communication line.

It should be noted that the present invention is not restricted to theabove-described exemplary embodiment, and various changes andmodifications may be made without departing from the scope of theinvention.

While the invention has been particularly shown and described withreference to exemplary embodiments thereof, the invention is not limitedto these embodiments. It will be understood by those of ordinary skillin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present invention asdefined by the claims.

This application is based upon and claims the benefit of priority fromJapanese patent application No. 2013-105981, filed on May 20, 2013, andJapanese patent application No. 2013-191772, filed on Sep. 17, 2013, thedisclosure of which is incorporated herein in its entirety by thisreference.

REFERENCE SIGNS LIST

-   10 BEARER MANAGEMENT DEVICE-   11 INCOMING CALL CONTROL UNIT-   15 SGW-   16 INCOMING CALL CONTROL UNIT-   17 DATA ACCUMULATION UNIT-   20 MOBILITY MANAGEMENT DEVICE-   21 LOCATION REGISTRATION AREA-   25 MME-   30 MOBILITY MANAGEMENT DEVICE-   31 LOCATION REGISTRATION AREA-   35 MME-   40 MOBILE TERMINAL DEVICE-   45 UE-   55 eNB-   65 eNB-   75 PGW

1. A mobile communication system including a terminal (UE), a MME (Mobility Management Entity) or a SGSN (Serving GPRS Support Node), and a SGW (Serving Gateway), comprising: the SGW sending a Downlink Data Notification message to the MME or the SGSN; and the MME or the SGSN sending a Downlink Data Notification Acknowledge message containing a cause value indicating a temporarily rejection due to mobility procedure to the SGW in response to the Downlink Data Notification message.
 2. A SGW (Serving Gateway) used in a mobile communication system including a terminal (UE) and a MME (Mobility Management Entity) or a SGSN (Serving GPRS Support Node), comprising: a unit configured to send a Downlink Data Notification message to the MME or the SGSN; and a unit configured to receive a Downlink Data Notification Acknowledge message containing a cause value indicating a temporarily rejection due to mobility procedure from the MME or the SGSN in response to the Downlink Data Notification message.
 3. (canceled)
 4. A communication method of a mobile communication system including a terminal (UE), a MME (Mobility Management Entity) or a SGSN (Serving GPRS Support Node), and a SGW (Serving Gateway), comprising: sending a Downlink Data Notification message from the SGW to the MME or the SGSN; and sending a Downlink Data Notification Acknowledge message containing a cause value indicating a temporarily rejection due to mobility procedure from the MME or the SGSN to the SGW in response to the Downlink Data Notification message.
 5. A control method for a SGW (Serving Gateway) used in a mobile communication system including a terminal (UE) and a MME (Mobility Management Entity) or a SGSN (Serving GPRS Support Node), comprising: sending a Downlink Data Notification message to the MME or the SGSN; and receiving a Downlink Data Notification Acknowledge message containing a cause value indicating a temporarily rejection due to mobility procedure from the MME or the SGSN in response to the Downlink Data Notification message.
 6. (canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled)
 11. (canceled)
 12. (canceled)
 13. The mobile communication system according to claim 1, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Tracking Area Update procedure with change of the MME is in progress when the MME receives the Downlink Data Notification message from the SGW.
 14. The mobile communication system according to claim 1, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Routing Area Update procedure with a change of the SGSN is in progress when the SGSN receives the Downlink Data Notification message from the SGW.
 15. The SGW according to claim 2, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Tracking Area Update procedure with a change of the MME is in progress when the MME receives the Downlink Data Notification message from the SGW.
 16. The SGW according to claim 2, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Routing Area Update procedure with a change of the SGSN is in progress when the SGSN receives the Downlink Data Notification message from the SGW.
 17. (canceled)
 18. (canceled)
 19. The communication method of a mobile communication system according to claim 4, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Tracking Area Update procedure with a change of the MME is in progress when the MME receives the Downlink Data Notification message from the SGW.
 20. The communication method of a mobile communication system according to claim 4, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Routing Area Update procedure with a change of the SGSN is in progress when the SGSN receives the Downlink Data Notification message from the SGW.
 21. The control method for a SGW according to claim 5, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Tracking Area Update procedure with a change of the MME is in progress when the MME receives the Downlink Data Notification message from the SGW.
 22. The control method for a SGW according to claim 5, wherein the cause value is used in the Downlink Data Notification Acknowledge message if Routing Area Update procedure with a change of the SGSN is in progress when the SGSN receives the Downlink Data Notification message from the SGW.
 23. (canceled)
 24. (canceled)
 25. The mobile communication system according to claim 1, wherein the SGW starts a locally configured guard timer upon receiving a message that the Downlink Data Notification message is temporarily rejected.
 26. The mobile communication system according to claim 25, wherein the SGW buffers an incoming packet to the UE and receives a Modified Bearer Request message.
 27. The mobile communication system according to claim 26, wherein the SGW sends the Downlink Data Notification message to the MME or the SGSN when receiving the Modified Bearer Request message.
 28. The mobile communication system according to claim 27, wherein the buffered packet addressed to the UE is released when the timer expires.
 29. A terminal (UE) used in a mobile communication system, the terminal comprising: a control unit that initiates a tracking area update procedure or a routing area update procedure with change of a MME (Mobility Management Entity) or a SGSN (Serving GPRS Support Node), and a reception unit that receives a paging from a base station or a radio control equipment, to which a paging message based on a Downlink Data Notification (DDN) message is transmitted from a new MME or a new SGSN after the change if the tracking area update procedure or the routing area update procedure is in progress when an old MME or an old SGSN before the change receives the DDN message for the UE.
 30. The mobile terminal (UE) according to claim 29, wherein the reception unit receives the paging after a tracking area update accept message or a routing area update accept message is received from the new MME or the new SGSN.
 31. A reception method of a terminal (UE) used in a mobile communication system, the method comprising: initiating a tracking area update procedure or a routing area update procedure with change of a MME (Mobility Management Entity) or a SGSN (Serving GPRS Support Node), and receiving a paging from a base station or a radio control equipment, to which a paging message based on a Downlink Data Notification (DDN) message is transmitted from a new MME or a new SGSN after the change if the tracking area update procedure or the routing area update procedure is in progress when an old MME or an old SGSN before the change receives the DDN message for the UE.
 32. The reception method of the terminal (UE) according to claim 31, wherein the UE receives the paging after a tracking area update accept message or a routing area update accept message is received from the new MME or the new SGSN. 